@kaspar030 do we need to do this if there are plans to remove mips RIOT-OS/RIOT#11788.

Otherwise, I was able to build the image but I have no hardware to test it.

Otherwise, I was able to build the image but I have no hardware to test it.

Could you provide some kind of test output?

do we need to do this if there are plans to remove mips RIOT-OS/RIOT#11788.

IMO that's just a suggestion. Removal of mips might happen later if it maintanance doesn't improve.

IMO that's just a suggestion. Removal of mips might happen later if it maintanance doesn't improve.

Ok I re-read the discussion thread, there doesn't seem to be a clear agreement yet.

Could you provide some kind of test output?

Since I have no hardware to test

We have a chicken and egg problem. The new toolchain from this PR fails on 2019.04. There's a fix in RIOT-OS/RIOT#11986. Anyhow, travis for this repo will (currently) always use 2019.04.

Ideas? Maybe first switch to 2019.07, then merge #11986, then backport to 2019.07-release?
Please let's not postpone merging this PR until 2019.10...
@MrKevinWeiss, it is "your release", what do you think?

Weren't we thinking about release specific tags for this repo anyways (#64)?

Ya, I think there were a few things that people still wanted in the release, at least @miri64 and @cladmi had some.

I downloaded the MIPS toolchain 2018.09-03 using the link found in the Dockerfile. I did a clean build of RIOT PR #12227, including the diff I mentioned in this PR. The board was printing the correct message over UART.

So if we trigger Murdock again, this should work now?

So if we trigger Murdock again, this should work now?

it should!

Somehow this exact PR gets scheduled to a travis worker that seems to be hopelessly overloaded...

The command "eval git clone --depth=50 https://github.com/RIOT-OS/riotdocker.git RIOT-OS/riotdocker " failed 3 times.
$ cd RIOT-OS/riotdocker
/home/travis/.travis/functions: line 109: cd: RIOT-OS/riotdocker: No such file or directory

😕

Now it went through! &go